Note

Low Risk
Observability-only changes to local draft file handling; no change to user-facing draft semantics or security-sensitive flows.

Overview
Adds ComposerDraftPersistenceError (Effect Schema.TaggedErrorClass) so mobile composer draft file I/O failures carry operation (open, read, decode, encode, write, hydrate), storage path, and the original cause.

Load, debounced save, and hydration paths still fail open (empty drafts / in-memory state unchanged), but silent catch blocks are replaced with console.warn that logs the tagged error. Writes now wrap failures in the structured error before the existing best-effort save handler logs them.

^{Reviewed by Cursor Bugbot for commit 0adc3f6. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Preserve mobile composer draft failures with structured error logging

• Introduces ComposerDraftPersistenceError, a tagged error class with fields for operation, directory, fileName, and cause, thrown by writePersistedComposerDrafts on open/encode/write failures.
• loadPersistedComposerDrafts now catches and wraps failures in ComposerDraftPersistenceError and emits a console warning, still returning an empty object on failure.
• savePersistedComposerDrafts and ensureComposerDraftsLoaded log console warnings on failure but continue to treat persistence as best-effort and do not rethrow.
• Changes are isolated to use-composer-drafts.ts.

^{Macroscope summarized 0adc3f6.}